Repository navigation
constitution: a development-only tool is not a one-way door - #198
Merged
Merged
Conversation
Needs the owner's OK (q-20261111-171117340-supervisor in stacks). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The owner, 2026-11-13: "yes, I rule that dev-only tools like linters don't need my approval. I've said this over and over again." new-dependency is owner-only and no standing rule can cover it, so each project kept asking. The constitution's one-way-door list now excludes dev-only tools, and the supervisor is told to decide them itself. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
hhff
marked this pull request as ready for review
November 13, 2026 19:43
Member
Author
|
The owner gave their OK directly in the upstream loop's session, 2026-11-13: "yes, I rule that dev-only tools like linters don't need my approval. I've said this over and over again. Why are these systems still asking me this". So the guardrail is satisfied without the Stacks Inbox question. I added a supervisor.md line: dev-only tools are the supervisor's own call, vetted and pinned (L-SEC-6/7), never asked. new-dependency is owner-only and no standing rule can cover it, which is why every project kept asking. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Needs the owner's OK: this would make a rule the owner gave stacks the default for every project. Their answer: question q-20261111-171117340-supervisor in stacks. Don't merge until it is answered yes by the owner (
questions --all --jsonin that repo:statusanswered,answered_byowner, and its question is the rule this PR changes).What
constitution.md §4 lists "a new top-level dependency, runtime, datastore or vendor" as a one-way door, so every project asks the owner before adding one. This exempts development-only tools: a linter, formatter, type checker or test helper that ships nothing to production.
Why
The operator's daily review found the same owner ruling in two projects. Stacks has "You don't need to ask me to add code quality / linting / dev tooling dependencies!". Stacksbot has it twice, the second time after being asked again: "I've already told you new dev tools can be added without asking me."
Tested
Docs only.
🤖 Generated with Claude Code